Document Path predicate fully expanded argument format#4116
Merged
ryanjbaxter merged 1 commit intospring-cloud:mainfrom Mar 27, 2026
Merged
Conversation
Add documentation for using the Path predicate with fully expanded arguments, including indexed key notation (patterns.0, patterns.1) for list parameters. This clarifies the naming convention when configuring routes via the Actuator API or programmatically. Fixes spring-cloudgh-3523 Signed-off-by: CheHyeonYeong <gusdudco6@naver.com>
CheHyeonYeong
force-pushed
the
docs/issue-3523-predicate-naming
branch
from
925c822 to
33c0239
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation for the Path route predicate factory's fully expanded argument format, clarifying the indexed key notation (
patterns.0,patterns.1) used for list parameters.Changes
patterns.0,patterns.1notationargsmap only accepts String key-value pairs and how list parameters are convertedContext
Users were confused about how to specify multiple path patterns when configuring routes programmatically or via the Actuator API, as the
argsmap requires String values but the predicate expects aList<String>for patterns.Closes #3523